Method for Detecting Video Tiling

ABSTRACT

A method for detecting errors on an audio/video (A/V) data stream in a data service network includes providing multicast components operably coupled to each other via respective links for transmitting the A/V data stream to a user and for defining at least one multicast tree. The method further includes generating a state information signal indicative of a number of errors on the A/V data stream for at least one of the links and at least one of the plurality of multicast components. The method further includes determining the cumulative number of errors on the A/V data stream that are indicative of the number of errors for the at least one of the links and the at least one of the plurality of multicast components in the multicast tree in response to the state information signal.

BACKGROUND

1. Field of the Invention

The embodiments of the invention described herein generally relate to a method for detecting errors on a data stream that may cause video tiles.

2. Background Art

Video tiling is generally defined as blocks or other such impairments present in a video output while displayed which distort a picture that is intended for viewing by a user. Service providers such as video and high speed data service providers struggle in determining the source of the tiles. Video tiling causes customers to believe there are problems with video receivers provided by the service providers. Customers often place service calls with the service providers and require the service providers to inspect and replace the video receivers in the customer's residence or place of business if the video tiling in the video output is substantial. In some cases, the video receiver may be functioning properly, but is nonetheless switched with another video receiver since the service provider is unable to determine the origin of errors within a multicast tree that cause video tiling.

A service provider network may include a number of multicast trees. Any given multicast tree in the network may include one or more video receivers operably coupled to one or more routers and one or more transmission sources. The video receivers, routers, and transmission sources are generally coupled to each via fiber links which span large distances. The transmission source transmits an audio/video (A/V) data stream to the routers via the links. The routers, in turn, direct the A/V data stream over the links to other routers or various video receivers. It is not uncommon while transmitting the A/V data stream for errors which produce video tiling to occur at the transmission source, the router, or the receiver. Such errors may also occur at the various links coupled between the transmission source, routers, and receivers located in the multicast tree. Existing approaches are not capable of providing service technicians the ability to determine the origin of errors in a multicast tree.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments of the present invention described herein are recited with particularity in the appended claims. However, other features will become more apparent and the embodiments of the present invention may be best understood by referring to the following detailed description in conjunction with the accompany drawings in which:

FIG. 1 depicts a system for detecting video tiles in accordance to one embodiment of the present invention;

FIG. 2 depicts a logical representation of a multi cast tree generated by the error detection device;

FIG. 3 depicts a method for displaying and reporting the number of error events detected by the system of FIG. 1; and

FIG. 4 depicts a method for detecting the root cause of the video tiles detected by the system of FIG. 1.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

FIG. 1 depicts a system 10 for detecting video tiling in accordance to one embodiment of the present invention. The exemplary system 10 includes a plurality of multicast trees 12 ₁-12 _(M) and an error identification device 14. For any given data service network, a service provider may provide audio visual data or high speed data to the plurality of multicast trees 12 ₁-12 _(M). Specific multicast trees may be designated to transmit audio visual data to various zones or regions within a particular country. Each multi cast tree 12 includes a transmission source 16 (12 ₁ has 16 ₁, 12 ₂ has 16 ₂ . . . 12 _(M) has 16 _(M)). The transmission source 16 is adapted to generate an A/V data stream. The A/V data stream comprises a plurality of packets. Each packet may include video or audio data (or both).

A plurality of routers 18 ₁-18 _(N) are adapted to receive the A/V data stream from each of the source 16 _(M). A plurality of receivers 20 ₁-20 _(O) are operably coupled to the routers 18 ₁-18 _(N). In the illustrated example, the router 18 ₁ directs the A/V data stream to the receiver 20 ₁. The router 18 _(N) directs the A/V data stream to the receivers 20 ₂ and 20 _(O). The receivers 20 ₁-20 _(O) are adapted to present the A/V data to an end user for viewing. The source 16 ₁, routers 18 ₁-18 _(N), and receivers 20 ₁-20 _(O) are generally defined as multicast components within the multicast tree 12 ₁ and co-act with each other to transmit the A/V data stream to an end viewer. In general, all references made specifically to the multicast tree 12 ₁ generally apply equally to the multicast trees 12 ₂-12 _(M). For example, each multicast tree 12 ₂-12 _(M) may include any number of multicast components such as the transmission source, the routers, and the receivers. It is generally understood that each multi cast tree 12 ₁-12 _(M) may include different or equal amounts of sources, routers, and receivers from one another. Further, the particular arrangement of the sources, routers, and receivers may vary or be similar to one another for each multicast tree 12 ₁-12 _(M).

Each multicast component (e.g., 16, 18 ₁-18 _(N), and 20 ₁-20 _(O)) in the multicast trees 12 ₁-12 _(M) are operably coupled together via a plurality of fiber links 19 ₁-19 _(P). With respect to the exemplary multicast tree 12 ₁, the source 16 ₁ and the router 18 ₁ are coupled together via the link 19 ₁. The router 18 ₁ and the receiver 20 ₁ are operably coupled together via the link 19 ₂. The source 16 ₁ and the router 18 _(N) are operably coupled together via the link 19 ₃. The router 18 _(N) and the receiver 20 ₂ are operably coupled together via the link 19 ₄. The router 18 _(N) and the receiver 20 _(O) are operably coupled together via the link 19 _(P). In general, each multicast component transmits the A/V data stream to the next multicast component downstream in the trees 12 ₁-12 _(M) via a corresponding link.

In addition, each receiver coupled to the source via a particular router is generally defined as a path within a given multicast tree 12 ₁-12 _(M). In the illustrated embodiment, the multicast tree 12 ₁ includes a total of three paths. The source 16 ₁, the link 19 ₁, the router 18 ₁, the link 19 ₂, and the receiver 20 ₁ form a first path. The source 16 ₁, the link 19 ₃, the router 18 _(N), the link 19 ₄, and the receiver 20 ₂ form a second path. The source 16 ₁, the link 19 ₃, the router 18 _(N), the link 19 _(P), and the receiver 20 _(O) form a third path. In general, each multicast tree 12 ₁-12 _(M) is generally adapted to include one or more paths for transmitting the A/V data stream to a user for viewing. Each link or path within a corresponding multicast tree 12 ₁-12 _(M) may span thousands of kilometers for a given region or part of the country. Errors attributed to the transmission of the A/V data stream within the network (e.g., from a source to a router and/or from a router to a receiver via corresponding links) in any given path may generate errors that may cause video tiling at a given receiver. In addition, a number of video impairments (or video tiling) may be due to fabric errors. Each router generally includes one or more interfaces (or line cards). A fabric (or communication path) is generally present between all line cards. Video tiling events may be caused due to problems on the fabric(s) present between the line cards. In some instances, the fabric may include intermittent transmission problems. Such problems may cause packet corruption or lead to packet(s) being dropped as the packet is transmitted from one line card to another (e.g., all line cards internal to the same router).

The error identification device 14 is operably coupled to the multicast trees 12 ₁-12 _(M) via a data communication line 17. The error identification device 14 is configured to determine the cumulative number of errors present within each link, path, and/or router of the multicast trees 12 ₁-12 _(M) so that service technicians can determine the growth of errors in a particular multicast tree 12 ₁-12 _(M) over any period of elapsed time. As note above, errors related to the router may be fabric errors. Such errors (transmission errors on the links and/or paths, and fabric errors associated with the routers) may contribute to the presence of video tiling at a receiver. With respect to the multicast tree 12 ₁, each router 18 ₁-18 _(N) is configured to transmit a state information signal for every directly connected link in the multicast tree 12 ₁ to the error identification device 14 via the data communication line 17.

The state information signal includes the number of packets transmitted and received from each multicast component (e.g., 16 ₁, 18 ₁-18 _(N), 20 ₁-20 _(O)) for the corresponding link and the number of packets received at each multicast component over the corresponding link with an error for every path in the multicast tree 12 ₁. For example, the router 18 ₁ may provide the number of packets successfully transmitted from the source 16 ₁ to the router 18 ₁ and the number of packets with errors received by the router 18 ₁ to the error identification device 14 with the state information signal. The router 18 ₁ may also provide the number of packets transmitted from the router 18 ₁ to the receiver 20 ₁ with an error to the error identification device 14 with the state information signal.

In addition, the router 18 ₁ may also include the number of packets that may be dropped due to errors in the state information signal. Such errors may be due to transmission issues (e.g., cyclic redundancy check (CRC) errors), interface overruns (e.g., contention for resources within the routers), transmission issues within each router (e.g., switch fabric errors), or output drops which are caused due to excessive loads on the transmitting interface. The router 18 ₁ obtains packet count information (e.g., packets lost due to CRC errors, fabric issues, etc.). As noted above, each router 18 ₁ and 18 _(N) generally includes a number of interfaces. Multicast content (e.g., A/V data stream) may flow over any one or more of the interfaces to a corresponding router 18 ₁ and 18 _(N). The routers 18 ₁ and 18 _(N) perform a CRC error coding scheme which adds redundant bits within the packets of the A/V data stream to indicate which packets in the A/V data stream includes an error for a particular multicast component.

CRC is generally defined as the process whereby a transmitting device embeds a calculation value along with audio and visual data in a packet in a data stream prior to transmitting the data stream. The receiving device repeats a similar calculation to obtain the similar calculation value for comparing the value embedded with the audio and video data in a packet after transmitting the data stream. If both the transmitting device and the receiving device obtain the same result, the particular packet transmitted is assumed to be error free. If the receiving device obtains a different result from that of the transmitting device, an error is presumed to have occurred and the packet is discarded.

In general, the routers 18 ₁ and 18 _(N) determine when an interface that belongs to a multicast component drops a packet. The routers 18 ₁ and 18 _(N) may be configured to report abstract errors which may result in packets being dropped. Such errors may be related to errors on the link or errors associated with the routers 18 ₁ and 18 _(N). Each router 18 ₁ and 18 _(N) is periodically queried by the error identification device 14 to transmit the state information signal over the data communication line 17 to the error identification device 14.

Each router 18 ₁-18 _(N) is also periodically queried by the error identification device 14 to transmit an identification signal over the data communication line 17 to the error identification device 14. Router 18 ₁ is generally configured to track packet data received and transmitted on interfaces belonging to the router 18 ₁. Likewise, the router 18 _(N) is generally configured to track packet data received and transmitted on interfaces that belong to the router 18 _(N). In general, each router 18 ₁ and 18 _(N) provides a local view of the multicast tree by tracking corresponding interfaces (e.g., which belong to each router 18 ₁ and router 18 _(N), respectively) for incoming and outgoing packets of multi cast content. Each router 18 ₁ and 18 _(N) transmits the tracked incoming and outgoing packets on a given interface over the identification signal to the error identification device 14. The error identification device 14 includes a correlation engine 22 for assembling the local views provided by each router 18 ₁ and 18 _(N) into a single end-to-end view (e.g., from source to receiver across each path) to generate an electronic logical representation of the multicast tree 12 ₁. In response to generating the logical representation of the multicast tree 12 ₁ (e.g., determining corresponding paths from the source to every receiver), the correlation engine 22 also associates the number of packets lost due to error.

The routers 18 ₁-18 _(N) are adapted to provide the tracked incoming and outgoing packets on a given interface by executing a protocol independent multicast (PIM) and an internet group membership protocol (IGMP). IGMP is generally defined as a signaling protocol that is used by any one or more of the receivers to express interest in a particular multicast group to a corresponding router. The router 18 ₁-18 _(N) use the PIM to build the multicast tree 12 ₁-12 _(M) from the receiver back to the transmission source. In general, the routers themselves may not understand what a particular multi cast tree looks like from the source to all receivers. Instead, a single router (or each router) understands the particular interface on which a specific multicast feed is expected to arrive and the interfaces the single router is expected to transmit the multicast content on. The correlation engine 22 gathers this information in response to querying the routers 18 ₁-18 _(N). The correlation engine 22 processes and combines this per router information into an end-to-end logical representation for each multicast tree 12-12. A user interface visually displays the logical representation for the multicast tree.

A database 24 is coupled to the error identification device 14 for storing information received via the state information signal and the identification signal. The error identification device 14 is adapted to calculate the cumulative number of errors for any link or path over a predefined time frame in response to receiving the state information signal. The error identification device 14 determines the cumulative number of errors based on errors present in the links, paths and/or the routers. The predefined time frame may correspond to the last N hours or days. The error identification device 14 is further configured to associate the cumulative number of errors for each link and path in the multicast trees 12 ₁-12 _(M) after generating the logical representation for each multicast tree 12 ₁-12 _(M). This characteristic will be discussed in more detail in connection with FIG. 2. The error identification device 14 allows a user to select a corresponding time frame (e.g., 1 hour, 7 hours, 24 hours, or 7 days) to view the cumulative number of errors for each link and path (via the user multicast component) within a particular multicast tree 12 ₁-12 _(M). The errors may be caused or attributed to various overdrive conditions at the multicast components within the routers, or by problematic fiber links in the network.

In general, the source 16 ₁ and the receivers 20 ₁-20 _(O) are configured to generate alerts as simple network management protocol (SNMP) traps in response to detecting errors while receiving the incoming A/V data stream. The source 16 ₁ and/or the receivers 20 ₁-20 _(O) transmit the alerts to the correlation engine 22 in response to detecting errors in real time (or asynchronously). The alerts generated by the source 16 ₁ and/or the receivers 20 ₁-20 _(O) may be indicative of whether a surge of errors are occurring over the network and whether there may be any new errors on any multicast component of the path from the source to the receiver. The correlation engine 22 receives the alerts and determines the particular multicast tree 12 ₁-12 _(M) that is impacted and displays such information to service personnel. In response to receiving the alerts, the correlation engine 22 may confirm the operational integrity of the affected multicast component, link or path in any or all of multicast trees 12 ₁-12 _(M). If errors on the path from the source to the receiver are confirmed and are temporally aligned with the alerts, then the correlation engine 22 may be adapted to alert service personnel as to the root cause of the errors to allow support personnel to fix or minimize the impact of the link or router errors.

FIG. 2 depicts an example of a logical representation of a multicast tree 12′ generated by the error identification device 14. The multicast tree 12′ includes a source 16′, a plurality of routers 18 ₁′-18 _(N)′, and a plurality of receives 20 ₁′-20 _(O)′. The source 16′, routers 18 ₁′-18 _(N)′, and receivers 20 ₁′-20 _(O)′ are coupled to each other via a plurality of links 19 ₁′-19 _(P)′. FIG. 2 illustrates that the link 19 ₁′ exhibits 56 errors over the last two hour period, 56 errors over the last four hour period, 143 errors over the last twenty-four hour period, and 1017 errors over the last seven day period. No additional errors were detected with respect to links 19 ₂′-19 ₈′. FIG. 2 depicts the detection of 784 errors over the last seven day period and no errors for the last two, four, and twenty-four hour periods for the link 19 _(P)′. In response to detecting number of errors for the link 19 _(P)′, the error identification device 14 determines that the cumulative number of errors for the path (e.g., 19 ₁′-19 _(P)′) is 56 errors for the last two hour period, 56 errors for the last four hour period, 143 errors for the last twenty-four hour period, and 1801 errors for the last seven day period. The errors visually displayed next to each link of FIG. 2 may be caused due to issues or errors related to the links, paths, and/or the routers.

FIG. 3 depicts a method 50 for displaying and reporting errors as detected by the system 10. In general, the method 50 is to be executed prior to utilizing the correlation engine 22 to receive alerts from the source 16 ₁ and the receivers 20 ₁-20 _(O).

In block 52, the error identification device 14 receives the identification signal from the routers in each multicast tree 12 ₁-12 _(M).

In block 54, the error identification device 14 (or the correlation engine 22) creates a logical representation for each multicast tree 12 ₁-12 _(M) (including all applicable multicast components and links) in response to the identification signal transmitted by the routers. For example, the error identification device 14 maps and derives all of the end-to-end paths for each multicast tree 12 ₁-12 _(M).

In block 56, the error identification device 14 determines the number of errors on each link 19 ₁-19 _(P) for a predefined time frame (e.g., 2 hours, 4 hours, 24 hours, 7 days, etc.).

In block 58, the error identification device 14 considers every path (e.g. from the source down to the receiver) in each multicast tree 12 ₁-12 _(M) to compute the cumulative number of errors for each path (which includes errors caused by the links, paths, and/or routers) in each multicast tree 12 ₁-12 _(M).

In block 60, the error identification device 14 outputs the visual logical representation for each multicast tree 12 ₁-12 _(M) via the user multicast component. The visual logical representation depicts the cumulative number of errors at each link and path for a predefined time frame.

In block 62, the error identification device 14 generates a web listing for each receiver impacted by the cumulative errors and sorts the receivers based on the number of errors detected per receiver. The error identification device 14 may generate the web listing into a color-coded matrix which indicates hot spots or potential problem areas for each multicast component in the multicast tree 12 ₁-12 _(M) that may be generating errors which result in video tiling. The user multicast component visually displays the listing.

FIG. 4 depicts a method 70 for receiving alerts based on errors present in the A/V data stream. The method 70 is generally executed after the error identification device 14 generates the logical representation for each multi cast tree 12 ₁-12 _(M).

In block 72, the correlation engine 72 is adapted to receive asynchronous (or event based) alerts or notifications from any one or more of the sources or receivers in the multicast trees 12 ₁-12 _(M) any time such errors are detected by the sources or receivers.

In block 74, the correlation engine 22 determines which multicast tree 12 ₁-12 _(M) from the logical representation of the multicast trees 12 ₁-12 _(M) includes a source or receiver that detects errors associated with the A/V data stream.

In block 76, the correlation engine 22 consults the logical representation for the affected multicast tree 12 ₁-12 _(M) as identified in block 74 to determine the corresponding paths from the source to each receiver for the affected multicast trees 12 ₁-12 _(M).

In block 78, the correlation engine 22 performs a real-time query on the applicable paths identified in block 76 to determine if there has been any recent network events which triggered the sources or receivers to transmit the alerts as noted in connection with block 72. Such network events may include hard or soft failures. The hard failures may include fiber line cuts, xenpack failures, transport issues, or central processing unit (CPU) spikes. The soft failures may include marginal xenpack transports, loose or dirty connections, or various component overloads (e.g., such overloads may be associated with application specific integrated circuits (ASICs), line cards, or fabric fibers).

In block 80, the correlation engine 22 attempts to determine the root cause for the errors based on whether recent network events (e.g., hard or soft failures) are detectable. If a recent network event (e.g., hard or soft failure) is detected, the method 70 moves to block 82. If a recent network event cannot be detected, the method 70 moves to block 84.

In block 82, the correlation engine 22 outputs the location (e.g., link and path) and the type of network event responsible for creating the error associated with the A/V data stream via the user multicast component.

In block 84, the correlation engine 22 determines that the root cause for the errors may be attributed with a particular transmission source in the affected multicast tree 12 ₁-12 _(M) or with the actual content that is flowing into a particular transmission source. In such a case, the correlation engine 22 outputs via the user multicast component that a network event was not detected and that the problem may be with a particular transmission source or the data flowing into the transmission source.

The embodiments of the present invention provide for an error identification device 14 which is capable of mapping multicast components, links, and paths for each multicast tree 12 ₁-12 _(M). The error identification device 14 is further adapted to receive the state information signal and the identification signal from routers 18 ₁-18 _(N) within each multi cast tree 12 ₁-12 _(M) to determine the cumulative number of errors per link and the cumulative number of errors per path and to provide a logical representation of such data (e.g., such errors may be attributed to the links, paths and/or the routers). The error identification device 14 provides the logical representation of the multicast trees 12 ₁-12 _(M) and the cumulative number of errors per link and path to allow service technicians to diagnose and troubleshoot problem areas based on the cumulative number of errors shown in the logical representation. In response to the error identification device 14 generating a logical representation of the multicast trees 12 ₁-12 _(M), the correlation engine 22 monitors the sources 16 ₁ and the receivers 20 ₁-20 _(O) in real-time for error alerts associated with the transmission of the A/V data stream. In response to such alerts, the correlation engine 22 provides service technicians the ability to determine the number of errors impacting each of the multicast trees 12 ₁-12 _(M) in real time before the errors associated with the transmission of the A/V data stream through the various links and paths grow into major problems. Such capability allows service technicians to troubleshoot and fix errors that may cause video tiling and may minimize exposure of the video tiling for the user.

While embodiments of the present invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the present invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the present invention. 

1-20. (canceled)
 21. A method, comprising: receiving, by at least one computing device, a message indicating an error detected in a network comprising plurality of multicast trees; determining, by the at least one computing device, a first multicast tree of the plurality of multicast trees that is affected by the error; determining, by the at least one computing device, a path of the first multicast tree that is affected by the error; and determining whether a known network event is associated with the determined path, and if so, generating for displaying an indication of the network event and a location of the network event in the network.
 22. The method of claim 21, wherein said location of the network event comprises the determined path.
 23. The method of claim 21, further comprising determining which link of a plurality of links in the determined path is associated with the network event, wherein said location of the network event comprises the determined link.
 24. The method of claim 21, further comprising determining a logical representation of a plurality of paths of the multicast tree, wherein said determining the path comprises determining the path based on the logical representation.
 25. The method of claim 21, wherein said message comprises an asynchronous message sent by a device of the network in response to the device detecting the error.
 26. The method of claim 25, wherein the device is part of the first multicast tree.
 27. The method of claim 21, wherein said generating for displaying comprises generating for displaying a graphical representation of at least a portion of the multicast tree, including the determined path.
 28. The method of claim 21, wherein the network event comprises a network event chosen from the following types of network events: a hard failure, and a soft failure.
 29. A method, comprising: generating, for each of a plurality of multicast trees of a network, a logical representation of paths in the multicast tree; responsive to detecting an error in the network, performing the following by at least one computing device: determining which one or more of the multicast trees are affected by the error; using at least one of the logical representations to determine which one or more of the paths of the determined one or more multicast trees are affected by the error; and determining whether there are any known network events associated with the determined one or more paths, and if so, determining at least one location of the network event based on the one or more paths and generating for displaying an indication of the at least one location of the network event.
 30. The method of claim 29, wherein said at least one location of the network event comprises at least one of the one or more paths.
 31. The method of claim 29, further comprising determining a link, from a plurality of links in at least one of the paths, that is associated with the network event, wherein said location of the network event comprises the determined link.
 32. The method of claim 29, further comprising receiving from the network, by the at least one computing device, a message indicating the error.
 33. The method of claim 29, wherein said generating for displaying comprises generating for displaying a graphical representation of at least a portion of at least one of the determined multicast trees, including the determined one or more paths.
 34. The method of claim 29, wherein the network event comprises a network event chosen from the following types of network events: a hard failure, and a soft failure.
 35. A method, comprising: receiving first data indicative of a plurality of errors in a multicast data stream that is propagating through a network; receiving second data indicative of a plurality of links in the network; determining by a computer a path through which the multicast data stream propagates, the path comprising at least some of the links; determining by the computer, for each of the links in the path, a cumulative number of the errors in the multicast data stream that occur along the respective link over a plurality of overlapping periods of time; determining by the computer, based upon the determined cumulative number of errors in each of the links in the path, a cumulative number of the errors in the multicast data stream that occur along the path over each of the periods of time; and generating for displaying a user interface that comprises: a graphical representation of the links coupled together in the path, an indication, for each of the graphically represented links, of the determined cumulative number of errors that occur along the respective link for each of the periods of time, and an indication of the determined cumulative number of errors that occur along the path for each of the periods of time.
 36. The method of claim 35, further comprising: determining, by the computer, a plurality of receivers in the multicast data stream that are impacted by the plurality of errors; and determining, by the computer, a web listing for each of the determined receivers.
 37. The method of claim 35, wherein said determining the path comprises determining the path from a plurality of paths, and wherein the method further comprises: performing, by the computer, and responsive to the errors, a real-time query of the determined path; and determining, by the computer, based on a network event identified as a result of the query, whether the network event triggered the errors.
 38. The method of claim 35, wherein said generating for displaying the graphical representation comprises generating for displaying the graphical representation as a plurality of nodes interconnected by a plurality of lines, the lines representing the links.
 39. The method of claim 38, wherein said generating for displaying the indications comprises generating for displaying each of the indications proximate to the line representing the link associated with the respective one of the indications.
 40. The method of claim 39, wherein the indications each comprise a textually-depicted numerical value. 